2.2.1.5 Other Data Integrator Capabilities
2.2.1.5.1 Record Recycling
Some source records may not be inserted or updated because either there are no parent or unconditional child records in the database, or there was an RDBMS error. The Data Integrator handles such load failures by writing them to a recycle file. The administrator can use this file along with other error files to determine the reason for failure. After making the necessary corrections, they can then optionally recycle these records.
2.2.1.5.2 Update Type Option
This feature allows the Data Integrator to perform sanity checks on the records without actually inserting or updating them. The Data Integrator retrieves the update type for the current loadset from the Rulebase. Based on the type, the Integrator can take any of the following actions:
| Update Type | Action |
| U | Update Only, No Inserts |
| I | Insert Only, No Updates |
| N | No Inserts or Updates |
| any other value | Insert/Update |
2.2.1.5.3 SQL Verbose
When the Data Integrator is invoked in verbose mode, it records to a file all SQL insert/update operations performed by the Integrator. In the case of RDBMS SQL Server errors, you can use this file to verify the SQL statements generated by the Data Integrator.
2.2.1.6 The Rulebase
The Rulebase is a Windows-based database that holds information necessary to load data into the IRE(TM) Marketing Warehouse. The proper functioning of the Data Loader depends on the legitimacy of the information stored in the Rulebase. The information stored in the Rulebase includes:
-
Names of all valid loadsets
Names of all input files that make a loadset
Names of all input fields
Starting position and field lengths of all input fields of an input record
Format, default values, and data types of all input fields
Names of output files
Names of output fields
Starting position, field length, and other data stipulations of the output fields
Database field that the output fields map to
Database tables that contain the database fields
Parent-child relationship definitions among database tables
Database fields (including the data types, data constraints, primary key indicator, and other provisions) that define the IRE(TM) Marketing Warehouse tables
Rules that define data source priority for a database field
Rules that define valid ranges for relevant database fields
Rules that define valid enumeration sets for relevant database fields
Rules that define logic to match input data records with existing records in database.
2.2.1.7 Incremental Index Updating
After adding or updating warehouse data, this feature allows the administrator to update the IRE(TM) Marketing Warehouse indexes in an incremental fashion. This removes the need to rebuild all the indexes from scratch, reducing the index update time from days to minutes.
[ Jump to Mercantile Software Systems' Web Site ]
Mercantile Software Systems, Inc.
371 Hoes Lane - Suite 102, Piscataway, NJ 08854 - (908) 981-1290 - email: Sales@mss.com
Copyright ©1995 Mercantile Software Systems, Inc. All Rights Reserved.
Previous
Table of Contents 
Next